home *** CD-ROM | disk | FTP | other *** search
- Path: solon.com!not-for-mail
- From: seebs@solon.com (Peter Seebach)
- Newsgroups: comp.std.c,comp.lang.c.moderated
- Subject: Re: printf() format extensions - looking for beta testers...
- Date: 14 Apr 1996 23:45:21 -0500
- Organization: Usenet Fact Police (Undercover)
- Sender: clc@solutions.solon.com
- Approved: clc@solutions.solon.com
- Message-ID: <4ksk91$rmr@solutions.solon.com>
- References: <4kgljv$l2p@solutions.solon.com> <4kobun$8i2@solutions.solon.com> <4koecq$8up@solutions.solon.com> <4kr7aj$kbs@solutions.solon.com>
- Reply-To: seebs@solon.com
- NNTP-Posting-Host: solutions.solon.com
-
- In article <4kr7aj$kbs@solutions.solon.com>,
- S. Lee <sl14@crux1.cit.cornell.edu> wrote:
- >Is it necessary to carry historical baggage by extending printf()? It
- >might be preferable to have a new function with new syntax so you don't
- >need to worry about backward compatibility.
-
- Not necessary; I just think it's desireable, because printf already does
- almost exactly what I want it to. I just want to extend it. I like
- the idea of being able to use user-defined types. (I dislike c++'s
- iostreams, because precision should be a function of a given print, not
- a stream; it is suboptimal to have to jump through hoops to print a
- number with precision of N without having to save and restore things.)
-
- -s
- --
- Peter Seebach - seebs@solon.com - Copyright 1996 Peter Seebach.
- C/Unix wizard -- C/Unix questions? Send mail for help. No, really!
- FUCK the communications decency act. Goddamned government. [literally.]
- The *other* C FAQ - http://www.solon.com/~seebs/c/c-iaq.html
-